2. Tails
3. wiki/src/doc/anonymous_internet/tor.*.po
4. Russian
5. Zen

[[!img tor.png link="no" class="svg" alt="A Tor connection goes through 3 relays with the last one establishing the actual connection to the final destination"]]

You cannot access the Internet from Tails until you are connected to Tor. For
example, *Tor Browser* displays the error message <span class="code">`Proxy
server refusing connections</span>` until you are connected to Tor.

You cannot access the Internet from Tails until you are connected to Tor. For example, *Tor Browser* displays the error message `Proxy server refusing connections` until you are connected to Tor.

<p>Because Tor routes your Internet traffic through 3 relays
before reaching its destination, the
connection is slower than when you are not using Tor.</p>

<p>See our documentation on
[[why Tor is slow|doc/anonymous_internet/tor/slow]].</p>

<h1 id="bridges">Tor relays and bridges</h1>

<h1 id="bridges">Tor relays and bridges</h1>

<h1 id="automatic">Connecting to Tor automatically</h1>

<h1 id="automatic">Connecting to Tor automatically</h1>

When you choose this option:

First, Tails synchronizes the clock of the computer automatically, because a correct time is needed to be able to connect to the Tor network.

Tails learns the current time by connecting to the captive portal detection
service of [Fedora](https://getfedora.org/), which is used by most Linux
distributions. This connection does not go through the Tor network and is an
exception to our policy of only making Internet connections through the Tor
network.

<p>You can learn more about our security assessment of this time
synchronization in our [[design documentation about non-Tor
traffic|contribute/design/Tor_enforcement#non-tor-traffic]].</p>

If you choose instead to [[hide that you are connecting to Tor|tor#hiding]],
you might have to fix the computer clock manually.

If Tails fails to synchronize the clock because you have to sign in to the network using a captive portal, an error screen is displayed that helps you do so.

- [[S For detailed instructions, see how to [[sign in to the network using a
captive portal|unsafe_browser]] - Configure a local proxy.

For detailed instructions, see how to [[sign in to the network using a
captive portal|unsafe_browser]].

WThen you choose this option, Tails tries different ways of connecting to Tor until it succeeds:

Then, Tails tries different ways of connecting to Tor until it succeeds:

Tails tries to connect to Tor directly using **public relays**, without using a bridges.

Tails tries to connect to Tor directly using **public relays**, without using a bridge.

Tails tries to connect to Tor using a set ofone of the **default bridges**, already included in Tails, if connecting using public relays fails.

Tails tries to connect to Tor using one of the **default bridges**, already included in Tails, if connecting using public relays fails.

<p>Tails uses the [[default <i>obfs4</i> bridges from <i>Tor
Browser</i>|https://gitlab.torproject.org/tpo/applications/tor-browser-build/-/blob/main/projects/tor-expert-bundle/pt_config.json?ref_type=heads]].</p>

If public relays and default bridges don't work, Tails asks you to configure a **custom bridges**, if connecting using the default bridges fails.

If public relays and default bridges don't work, Tails asks you to configure a **custom bridge**, if connecting using the default bridges fails.

<h1 id="hiding">Hiding to your local network that you are connecting to Tor</h1>

<h1 id="hiding">Hiding to your local network that you are connecting to Tor</h1>

When you choose this option, Tails will only connect to Tor after you configure a Tor bridges. Bridges are secret Tor relays that hide that you are connecting to Tor.

When you choose this option, Tails will only connect to Tor after you configure a Tor bridge. Bridges are secret Tor relays that hide that you are connecting to Tor.